Skip to content

Document Mixpanel data residency region option#6301

Closed
aicortez wants to merge 1 commit into
mainfrom
alejandro/mixpanel-region
Closed

Document Mixpanel data residency region option#6301
aicortez wants to merge 1 commit into
mainfrom
alejandro/mixpanel-region

Conversation

@aicortez

@aicortez aicortez commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Documents the optional region property (us | eu | in) on the Mixpanel integration page, so customers can route analytics to the correct regional servers for data residency compliance. Adds the property to the docs.json example and a short "Data residency" section covering accepted values and the US default.

🤖 Generated with Claude Code


Note

Low Risk
Documentation-only change to the Mixpanel integration page with no runtime or configuration code modified in this diff.

Overview
Updates the Mixpanel integration docs so customers can configure data residency via an optional region field in docs.json.

The docs.json example now includes "region": "eu" alongside projectToken. A new Data residency section explains that region accepts us (default), eu, and in, routes events to the matching Mixpanel regional servers, and must align with the project's configured residency or events may not be recorded.

Reviewed by Cursor Bugbot for commit 29ad91e. Bugbot is set up for automated code reviews on this repo. Configure here.

Adds the optional `region` property (us | eu | in) to the Mixpanel
integration docs so customers can route analytics to EU/IN servers for
data residency compliance.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@mintlify

mintlify Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
mintlify 🟢 Ready View Preview Jun 26, 2026, 8:39 PM

@mintlify

mintlify Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
smartac 🟢 Ready View Preview Jun 26, 2026, 8:38 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@mintlify

mintlify Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
testsignup415 🟢 Ready View Preview Jun 26, 2026, 8:30 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@mintlify

mintlify Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
adminroletesting 🟢 Ready View Preview Jun 26, 2026, 8:39 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@mintlify

mintlify Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
hfh-d7a4d643 🟢 Ready View Preview Jun 26, 2026, 8:40 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@mintlify

mintlify Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
gwgwgw 🟢 Ready View Preview Jun 26, 2026, 8:39 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@mintlify

mintlify Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
tomee 🟢 Ready View Preview Jun 26, 2026, 8:39 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@ethanpalm

Copy link
Copy Markdown
Collaborator

#6297 adds this, so closing. thank you for creating the pr though!

@ethanpalm ethanpalm closed this Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants